| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.2.8.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.8 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_2_8_Support_Medical_Device_Originated_Data |
| Title | CPS.2.8 Support Medical Device Originated Data (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Support collection and presentation of data captured from medical and medication monitoring devices. |
| Purpose | Collection of medical device information is supported as appropriate to the care setting. Examples include: vital signs/pulse-oximeter, anesthesia machines, home diagnostic devices for chronic disease management, laboratory machines, bar coded artifacts (e.g., medicine, immunizations, demographics, history, and identification), transcranial magnetic stimulation systems, or medication reminder systems. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Support collection and presentation of data captured from medical and medication monitoring devices.
Collection of medical device information is supported as appropriate to the care setting. Examples include: vital signs/pulse-oximeter, anesthesia machines, home diagnostic devices for chronic disease management, laboratory machines, bar coded artifacts (e.g., medicine, immunizations, demographics, history, and identification), transcranial magnetic stimulation systems, or medication reminder systems.
| CPS.2.8#01 | dependent SHALL |
The system SHALL provide the ability to capture electronic data from medical devices according to scope of practice, organizational policy, and/or jurisdictional law. |
| CPS.2.8#02 | SHALL |
The system SHALL provide the ability to render information collected from medical devices as part of the medical record. |
| CPS.2.8#03 | SHOULD |
The system SHOULD provide the ability to capture and maintain the following information of a device when it is suspected as the cause of a Serious Adverse Event: brand name, common device name, manufacturer, model number, catalog number, serial number, lot number, expiration date, other number(s), operator of device, if implanted (date), if explanted (date), single or multiple use device indicator (i.e. if this is a single use device that was reprocessed and reused on a patient). |
| CPS.2.8#04 | dependent SHOULD |
The system SHOULD provide the ability to present data captured from medical devices for verification by a provider according to scope of practice, organizational policy, and/or jurisdictional law, and present the identification of the relevant device. |
| CPS.2.8#05 | SHOULD |
The system SHOULD link data that was captured by a medical device to the originating device ID and device type. |
| CPS.2.8#06 | SHOULD |
The system SHOULD provide the ability to capture the date/time from medical devices. |
| CPS.2.8#07 | SHOULD |
The system SHOULD provide the ability for the user to capture data manually from medical devices. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.2.8",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support collection and presentation of data captured from medical and medication monitoring devices.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Collection of medical device information is supported as appropriate to the care setting. Examples include: vital signs/pulse-oximeter, anesthesia machines, home diagnostic devices for chronic disease management, laboratory machines, bar coded artifacts (e.g., medicine, immunizations, demographics, history, and identification), transcranial magnetic stimulation systems, or medication reminder systems.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture electronic data from medical devices according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render information collected from medical devices as part of the medical record.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain the following information of a device when it is suspected as the cause of a Serious Adverse Event: brand name, common device name, manufacturer, model number, catalog number, serial number, lot number, expiration date, other number(s), operator of device, if implanted (date), if explanted (date), single or multiple use device indicator (i.e. if this is a single use device that was reprocessed and reused on a patient).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to present data captured from medical devices for verification by a provider according to scope of practice, organizational policy, and/or jurisdictional law, and present the identification of the relevant device.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD link data that was captured by a medical device to the originating device ID and device type.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture the date/time from medical devices.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.2.8#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the user to capture data manually from medical devices.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.2.8",
"version" : "2.1.0",
"name" : "CPS_2_8_Support_Medical_Device_Originated_Data",
"title" : "CPS.2.8 Support Medical Device Originated Data (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Support collection and presentation of data captured from medical and medication monitoring devices.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Collection of medical device information is supported as appropriate to the care setting. Examples include: vital signs/pulse-oximeter, anesthesia machines, home diagnostic devices for chronic disease management, laboratory machines, bar coded artifacts (e.g., medicine, immunizations, demographics, history, and identification), transcranial magnetic stimulation systems, or medication reminder systems.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CPS.2.8-01",
"label" : "CPS.2.8#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture electronic data from medical devices according to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.5#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.8-02",
"label" : "CPS.2.8#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render information collected from medical devices as part of the medical record.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.5#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.8-03",
"label" : "CPS.2.8#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain the following information of a device when it is suspected as the cause of a Serious Adverse Event: brand name, common device name, manufacturer, model number, catalog number, serial number, lot number, expiration date, other number(s), operator of device, if implanted (date), if explanted (date), single or multiple use device indicator (i.e. if this is a single use device that was reprocessed and reused on a patient)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-CPS.2.8-04",
"label" : "CPS.2.8#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to present data captured from medical devices for verification by a provider according to scope of practice, organizational policy, and/or jurisdictional law, and present the identification of the relevant device."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.8-05",
"label" : "CPS.2.8#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD link data that was captured by a medical device to the originating device ID and device type."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.8-06",
"label" : "CPS.2.8#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture the date/time from medical devices."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.2.8-07",
"label" : "CPS.2.8#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the user to capture data manually from medical devices."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.